Skip to main content

2024-02 Release Notes

Iteration: 2024-02

February 20th, 2024


Whats New?

5458Sales Importer Enhancements BETA
\(^▽^)/Enrollments API: Renewal Endpoint (^▽^)/

Improvements

5906Autopay Pending Autoresponder
6015Added replacement values for [LETTER_GENERATION_MONTH] and [LETTER_GENERATION_YEAR].
\(^▽^)/Plans Manager: Improved sidebar so only Markets/Utilities with published plans are displayed by default.
\(^▽^)/Plans Manager: Removed plan count from sidebar. Added edit quick access for Market/Utility instead. 
\(^▽^)/Enrollments API: Added validations for customer passwords.
\(^▽^)/Payment Gateway: Revamped success and error messages.
\(^▽^)/Performance and Refactor improvements: Merged code from the different enrollment journeys. 
\(^▽^)/Performance and Refactor improvements for the method that takes care of retrieving customer’s payment profiles.
\(^▽^)/Enrollment Details: Rearranged payment section.

Fixes 

5850Adjustments for the Renewal Process through MyAccount that was showing an incorrect logo and a pop-up that was supposed to be only visible for agents.
5968Fix for “Nullable Object must have a value” error message on Sales Importer.
5992Adjusted a validation that prevented linking accounts.
5995Resolved an issue that prevented users from renewing gas accounts.
6003Corrected an error message that would appear when trying to add an IP to an existing Partner Account.
6035Adjusted URL in Reset Password autoresponder so it shows CLICK HERE TO RESET YOUR PASSWORD and it's displayed correctly on some email providers such as Hotmail.
6000Reset Password link is kept during a 90 minutes period so that no matter how many Reset Password emails are generated, the url stays the same.
¯\_(ツ)_/¯Fixed an issue in the Web Enrollment Journey where the Credit Check UI was not displayed.
¯\_(ツ)_/¯Enrollments API: Adjusted the Recurring Billing setup that was incorrectly calling methods when the enrollment hadn’t been submitted to the billing system yet.
¯\_(ツ)_/¯Enrollments API: Correction for trace logs.
¯\_(ツ)_/¯Adjustment on Brand Management: Values were not refreshed after updates.
¯\_(ツ)_/¯Corrected some typos on the 2FA functionality.
¯\_(ツ)_/¯Adjusted how the plan version is displayed on the Edit Plan pop up to avoid confusion.

Features & Fixes Details

Sales Importer Enhancements BETA

This release includes the BETA version of the new Sales Importer. This version will coexist with the current Sales Importer until a final stable version is released. We suggest using this new version with a small number or enrollments and users can always go back to the current Importer to massively import accounts.

At first, this new version may appear more complex or with more steps than the regular version, however, once new automation processes are put in place, the import process will be smoother. 

The importer has a set of tabs to classify enrollments based on transactions: New Enrollments, Winbacks, Renewals, Rescinds, Duplicates. Users have the possibility of moving enrollments from one tab to another.

Feel free to provide feedback on this new functionality so we can improve it!

Enrollments API: Renewal Endpoint

Though the Renewal endpoint already exists in MyAccount, with this new release it is possible for third parties to use the Renewal endpoint without MyAccount. This endpoint is accessible with the Customer OR Plans_And_Rates roles.

There’s also a new endpoint to validate if an enrollment is renewable for a provided LDC and plan.

The specifications for the API changes can be found here. Please, make sure to share this document with all third parties currently using OpsAdmin API.

Plans Importer

This new functionality allows users to massively create plans in the system. It works the same way as other importers in OpsAdmin: There is a fixed template that must be populated and imported to the system. There are tons of validations in place to assure data consistency. The Importer can be found under the Data Tools menu.

One thing to consider is that the purpose of this functionality is to create NEW plans from scratch. This can be helpful during an implementation phase or maybe after setting up a new utility in the system. There is no validation against existing plans. If users need to update existing plans, Global Price Changes is the place for that. Not here.

Template 

Users should download the template from the Importer UI to make sure they are using the latest version of the file.

The file has comments on each header explaining to users how each column should be populated. It is very important that columns are filled with valid values in order to speed up the import process and avoid having to make corrections. Data should be full text format and only the first tab should be populated. To save server disk space and speed up the import process, no other tab should be filled with data.

Here’s a brief summary of each column. 

  • Plan Scope: Valid values are WEB PLAN, NON WEB PLAN, AUTORENEWABLE PLANS. This field indicates if the plan is visible for customers on a website or Enrollment Journey. 

  • Plan name: This is the field displayed in the different enrollment journeys, for example: Super Green Plan 24, Affordable 12, etc. 

  • Utility: This field should be populated with a valid existing Utility from OpsAdmin using the Utility Billing System field from Utility Manager. For example: Pepco DC, United Illuminating.

  • Commodity: Commodity name such as Natural Gas, Electricity - 100% Renewable.

  • Customer Type: Residential, Small Business, Large Business

  • Billing Type: LDC Consolidated Bill Ready, Utility Rate Ready.

  • Term: This is the description of the term for those non numeric terms or just the numeric value. Examples: 12, 24, 36, Affordable Wind Through 4/30/2020.

  • Plan Type: FiXED, VARIABLE, DAILY RATE.

  • Billing System Code: The plan code that is going to be submitted to the billing system, for example: COMED_E_R_FIXED_GRN0_0MSF_0ETF_6T_5.38KWH_BR

  • Default Plan: This must be the Default Plan ID that the new plan will be pointing to.

  • Monthly Fee, Rate, Cancellation Fee, Risk free trial period: All of these are just the numeric value.

  • Cancellation Fee Type: ANNUAL, DAILY, MONTHLY, FIXED VALUE.

  • Early Termination Text: This is just a text value.

  • Start Date, End Date, Variable Effective From: Users should respect the yyyy-MM-dd format. For example: 2024-02-25.

  • Is Affiliate: Can be True or False if users are creating affiliate plans.

  • Affiliate: This should be the Affiliate PROMO CODE. Example: POWER, POWERTOCHOOSE.

  • Id Affiliate Parent Plan: Users should populate with the parent plan ID when creating affiliate plans. If not populated, the system will try to locate the parent but we suggest providing the parent ID to speed up the process.

  • Publish: True or False.

  • Send Dates to Billing System: True or False.

  • Traunch Calculation Type: Can be AllIn or Passthrough.

  • Automatically Add Acceptance: True or False to inherit acceptance values from Utility.

Processing

After carefully filling the template, it can be imported using the Import Plans File button:

alt text

The System will perform several validations to ensure data integrity and consistency.

Autopay Pending Autoresponder

Currently, OpsAdmin has an autoresponder trigger to send notifications when a deposit is pending at the moment of saving the enrollment. There is no similar trigger for recurring billing because in the past autopay was mandatory and not possible to generate the enrollment without subscribing to autopay.

With this new Release, OpsAdmin includes the Payments: Recurring Billing Required trigger. The autoresponders with this trigger will be generated when an enrollment is saved but not sent to the billing system because OpsAdmin is waiting for the customer to subscribe to recurring billing. The logic will be mostly the same whether the enrollment is created using the Web Enrollment Journey, Quick enrollments, Sales Importer or API. The autoresponder will be sent:

  • If recurring billing is mandatory regardless of whether the customer agreed to subscribe or not.

  • If recurring billing is optional and the customer chose to subscribe.